Release 10.1A: OpenEdge Application Server:
Administration

Using the query option to check status

You can test your configuration and check its status by running the -query option on the AdminServer, NameServer, and the WebSpeed Transaction Server.

To query the AdminServer, use the PROADSV utility, which is installed in install-path/bin, as shown:

proadsv -query

To query a local NameServer, use the NSMAN utility, which is installed in install-path/bin, as shown:

nsman -name NameServer-name -query

To query a remote NameServer, add the following parameters to the command, as shown:

nsman -name NameServer-name -host host-name -port port -user user-name -query

To query a local WebSpeed Transaction Server, use the WTBMAN utility, which is installed in install-path/bin, as shown:

wtbman -name ts-name -query

Where ts-name is the name of the Transaction Server that you want to query. You can have more than one Transaction Server running on a single machine.

To query a remote WebSpeed Transaction Server, add the following parameters to the command:

wtbman -name ts-name -host host-name -port port -user user-name -query

The query reports on the Transaction Server’s pool of WebSpeed agents. For each agent, it lists a process ID, its port number, its status, how many requests it has serviced, when it started, and when its status changed. These are the agent status types:

AVAILABLE — The agent is available to execute application logic.
BUSY — The agent is actively executing application logic (Web object) for a Web user.
LIMBO — The agent is in a transitional state. If the status persists, it indicates an error condition.
LOCKED — The agent is dedicated to a particular Web browser and is only available to the browser whose application locks it.
STARTING — The broker has launched the agent, but the agent has not yet initialized.